Skip to content

feat(aws-devops-agent): send review_depth for code change risk analyses - #215

Merged
nadetastic merged 2 commits into
kirodotdev:mainfrom
amznUjjwalpa:review-depth
Nov 12, 2026
Merged

nadetastic merged 2 commits into
kirodotdev:mainfrom
amznUjjwalpa:review-depth

Conversation

@amznUjjwalpa

Copy link
Copy Markdown
Contributor

Description

Stacked on #211. This branch contains #211's commit plus one more; review only the last commit, "feat(aws-devops-agent): send review_depth for code change risk analyses". Merge #211 first.

The DevOps Agent MCP server's create_code_change_risk_analysis tool now takes an optional review_depth: static-analysis or verification-testing. This switches the aws-devops-agent power's release readiness steering from skip_automated_testing to review_depth.

  • Spec mode still always runs static analysis only (review_depth="static-analysis"). Vibe mode still asks the user whether they want a quick static analysis or a full analysis with automated testing, and passes static-analysis or verification-testing from the answer. Only the parameter changes.
  • The table explains that automated testing runs only on repositories where it is enabled in the agent space.
  • The aws-mcp fallback writes metadata.reviewDepth together with the matching metadata.skipAutomatedTesting, so it behaves the same with review agents that only read the older flag.

skip_automated_testing still works on the server, so older copies of this power keep working.

Testing

Ran the MCP server's review_depth handling against a gamma agent space: both values and leaving it out, through both create_code_change_risk_analysis and the older create_release_readiness_review, and read back the task metadata.

…e risk analysis

Release readiness review is now called code change risk analysis.

- Call the code change risk analysis tools (create_code_change_risk_analysis,
  list_code_change_risk_analyses, cancel_code_change_risk_analysis,
  get_code_change_risk_analysis_report). The server picks the task type.
- Use the new name when talking to users, and still recognize the old one.
- Find an earlier analysis with list_code_change_risk_analyses.
- The aws-mcp fallback creates CODE_CHANGE_RISK_ANALYSIS tasks.
The skill sends review_depth instead of skip_automated_testing:
static-analysis for a quick or static-only review, verification-testing
for a full review with tests. The CLI fallback writes metadata.reviewDepth
with the matching metadata.skipAutomatedTesting.
@nadetastic
nadetastic merged commit 790bfea into kirodotdev:main Nov 12, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants